Tips, Tricks, and Notes for Tracealyzer

This topic contains important things to consider when using Tracealyzer for RTX64.

Tips and Tricks

• You can force Tracealyzer to only display columns that contain data. To do this, right-click on the Tracealyzer main window background and then click Hide empty columns.

• You can combine multiple horizontal views using Views > Add > (graph type).

• By default, Raw Monitoring Framework Events are included in the trace. However, to see these events in the Trace View you must turn on their display in the View Filter. To do this, select the Raw Data Events check box.

IMPORTANT! Including raw events may significantly increase memory usage and loading time.

See Raw Monitoring Framework Events for more information.

Notes

• Ensure that Context Switch events are enabled. When Context Switch events are not enabled, the following issues might occur:
• Tracealyzer data may be ambiguous.
• The CPU Load Graph may show incorrect CPU usage data.
• In Tracealyzer, custom events generated by RtGenerateEvent are displayed as user events.
• Tracealyzer does not display Ex versions of RTX64 supported functions. Only base versions are shown.

For example, RtCreateTimerEx will appear as RtCreateTimer

• The RTX64 supported functions Sleep, RtSleepEx, and RtSleepFt are all displayed as RtSleepFt in Tracealyzer. The units for the sleep period are always shown in 100 ns intervals, which is the unit used by RtSleepFt.
• Columns displayed with a stippled effect in the main window do not correspond to RTX64 events or behaviors.
• An SRI event indicates that the Subsystem is requesting a service from Windows or Windows is requesting a service from the RTX64 Subsystem. This call is not deterministic. Windows activity could be impacting your real-time application at this location.
• If you open a monitor session file from RTX64 3.x in Tracealyzer for RTX64 version 4.2 or later, you will see the corresponding 4.x function names, not the 3.x function names.